Also, since nobody has ever opened a pull request here I'm not sure if the CI is designed to handle PR OpenBLAS builds gracefully & if the cost of building a PR and then merging / building again is undesirably high.

One other question -- are the manual processing steps for MacOS platform still needed?

I never much enjoyed those 'build-passing' badges, partly because the builds could fail for no good reason - but if you like them, please go ahead.

No - there's no need for the manual processing steps for the Mac library now, we aren't shipping dual-arch any more.

PRs are fine, I think. It's not crazy long, and there won't be many PRs, I don't suppose.

Builds look ok to me, but PRs don't seem to have access to the secret API key needed to upload to the server.

I suppose that makes sense--otherwise anyone could open a PR and start dumping files on the server. So, if this looks good to you, presumably it has to be merged for the uploads to happen.

Well - I think the API key is encrypted to the repo - so I think that PRs from the main repo, to the same repo but master branch, will upload, but I might be wrong.

You can check the wheelhouse upload command logs near the end of this PR CI builds vs. your last push to master to see the difference, I think. There's a warning on the PR but not on your pushes.

Right - I would have predicted that because the PR comes from your repo. If you'd made a branch in this MacPython repo, and then done a PR from that, I would predict an upload. But I'm speculating.

Wouldn't I need commit rights to push the branch to the repo to open the PR? That was the motivation for the fork in the first place.

Yes, right - and you're welcome to those if you don't have them - but it would only be necessary if you needed the upload as part of the PR. I'm guessing that usually the PRs will be getting the build steps right, and the upload will only be needed after the merge.

That sounds right. If I work with you / Carl eventually to make less trivial adjustments to the build then uploading by default would not be desirable on more substantive PRs I suspect.

Are you happy to merge this or do you want more changes here?

Yes, all good ..